Skip to content

Build CBMC in Visual Studio 2019, in Github Actions. #5459

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 19, 2020

Conversation

NlightNFotis
Copy link
Contributor

  • Each commit message has a non-empty body, explaining why the change was made.
  • Methods or procedures I have added are documented, following the guidelines provided in CODING_STANDARD.md.
  • The feature or user visible behaviour I have added or modified has been documented in the User Guide in doc/cprover-manual/
  • Regression or unit tests are included, or existing tests cover the modified code (in this case I have detailed which ones those are in the commit message).
  • My commit message includes data points confirming performance improvements (if claimed).
  • My PR is restricted to a single feature or bugfix.
  • White-space or formatting changes outside the feature-related changed lines are in commits of their own.

@@ -21,3 +21,22 @@ jobs:
run: cd build; ninja
- name: Run CTest
run: cd build; ctest -V -L CORE .
check-vs-2019-build-and-test:
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The name of the action is build-and-test because I'm already working on building and running tests on Github Actions under vs2019, but the running tests part is not there yet - however, since the building CBMC is already done, we figured we could publish this part of the work, and get the rest of it merged as it's finished.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don’t think this needs to be called ‘build-and-test’, the other jobs in here are called ‘check’-somethingsomething and I think building and testing should be implied.

If you’re doing something other than building and testing that should be called out.

Copy link
Contributor

@thomasspriggs thomasspriggs Aug 14, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⛏️ Given that testing isn't part of this PR, we should probably name this check-vs-2019-build-only, so that there is no confusion in the interim between the two PRs. It can just be renamed again, when the second PR comes.

shell: cmd
steps:
- name: Checkout the repository
uses: actions/checkout@v2

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
uses: actions/checkout@v2
uses: actions/checkout@v2
with:
submodules: recursive

uses: actions/checkout@v2

- name: Update the submodules
run: git submodule update --init

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Apply above suggestion then this step isn’t needed anymore

run: git submodule update --init

- name: Install bison and flex
run: ${{env.SCRIPT_DIR}}\install-bison.bat

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It’s in env, so this really should be %SCRIPT_DIR%

run: ${{env.SCRIPT_DIR}}\install-bison.bat

- name: Build cbmc
run: ${{env.SCRIPT_DIR}}\build-cbmc.bat

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ditto

Copy link
Contributor

@thomasspriggs thomasspriggs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⛏️ When I was checking through the build log I noticed that it stated "Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE) ". So It may be worth adding a doxygen install.

@@ -21,3 +21,22 @@ jobs:
run: cd build; ninja
- name: Run CTest
run: cd build; ctest -V -L CORE .
check-vs-2019-build-and-test:
Copy link
Contributor

@thomasspriggs thomasspriggs Aug 14, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⛏️ Given that testing isn't part of this PR, we should probably name this check-vs-2019-build-only, so that there is no confusion in the interim between the two PRs. It can just be renamed again, when the second PR comes.

@codecov
Copy link

codecov bot commented Aug 18, 2020

Codecov Report

Merging #5459 into develop will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff            @@
##           develop    #5459   +/-   ##
========================================
  Coverage    68.22%   68.22%           
========================================
  Files         1178     1178           
  Lines        97580    97580           
========================================
  Hits         66573    66573           
  Misses       31007    31007           
Flag Coverage Δ
#cproversmt2 42.79% <ø> (ø)
#regression 65.39% <ø> (ø)
#unit 32.26% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.


Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update af5bc99...a6ca1ab. Read the comment docs.

submodules: recursive

- name: Install bison and flex
run: %SCRIPT_DIR%\install-bison.bat

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 This doesn’t run right now due to a yaml parsing error (apparently % is not allowed in plain context). Write this as either

Suggested change
run: %SCRIPT_DIR%\install-bison.bat
run: "%SCRIPT_DIR%\\install-bison.bat"

or

Suggested change
run: %SCRIPT_DIR%\install-bison.bat
run: |
%SCRIPT_DIR%\install-bison.bat

@NlightNFotis NlightNFotis force-pushed the vs-github-action-build branch from aeb0ccd to a6ca1ab Compare August 18, 2020 16:07
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@NlightNFotis NlightNFotis merged commit e06f678 into develop Aug 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants